Attribution issue

• issueId: issue_mo8ywjss_siyh6g
• category: tool
• canonicalTitle: MCP createCloudFunction 工具参数设计不清晰导致 HTTP 云函数创建失败
• representativeRun: atomic-js-cloudbase-http-function-params/2026-04-21T18-38-57-1k9fho

Automation summary

• root_cause: The MCP manageFunctions tool's parameter descriptions for createFunction action were unclear about what fields are required for HTTP cloud functions. Specifically: (1) The func parameter description didn't explain which fields are required for HTTP functions (type, protocolType, runtime), and (2) The functionRootPath parameter description didn't clearly indicate it's required (along with zipFile) when creating HTTP functions.
• changes: Applied the fix from PR fix: MCP createCloudFunction 工具参数设计不清晰导致 HTTP 云函数创建失败 #623 to mcp/src/tools/functions.ts:

1. Enhanced func parameter description to clearly list required fields for HTTP functions: name (required), type: "HTTP", protocolType: "HTTP" (or "WS" for WebSocket), runtime (recommended "Nodejs18.15")
2. Added a warning to functionRootPath description that it's required for HTTP functions when zipFile is not provided

• validation:
• TypeScript compilation: tsc --noEmit passes without errors
• Skill tests: All 10 tests pass (build-skills-repo, build-compat-config, skill-quality-standards)
• follow_up: The fix is a Layer 1 change (improving tool descriptions) that makes HTTP function creation requirements explicit in the M

Changed files

• mcp/src/tools/functions.ts